-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cilium] Add support for choosing resources #11248
Conversation
Hi @dntosas. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
a13ae2a
to
db3a3b1
Compare
db3a3b1
to
e3c625a
Compare
b58ff32
to
2edead1
Compare
/retest |
2edead1
to
34a8109
Compare
533f3c7
to
e3bcced
Compare
it seems we hit AWS limits again in test jobs like kubernetes/k8s.io#1921 |
/retest |
a90c694
to
0f0404c
Compare
cf371ec
to
cd32964
Compare
/retest |
@@ -87,6 +87,8 @@ Then we conditionally move cilium-operator to masters: | |||
{{ '{{ end }}' }} | |||
``` | |||
|
|||
After changing manifest files remember to run `bash hack/update-expected.sh` in order to get updated [manifestHash](https://github.com/kubernetes/kops/blob/master/upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/cilium/manifest.yaml#L74) values. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making this bit more clear. Note that not all manifests have tests that requires update-expected
.
Perhaps split this to a dedicated commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
docs/networking/cilium.md
Outdated
cilium: | ||
cpuRequest: "25m" | ||
memoryRequest: "128Mi" | ||
cpuLimit: "100m" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting limits on system pods is a bit risky. I'd rather not allow it. It is better that cilium consumes more memory than expected rather than that it OOMs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed limits ^^
Signed-off-by: dntosas <ntosas@gmail.com>
cd32964
to
08aa29e
Compare
08aa29e
to
2de7866
Compare
Cilium as a CNI is a critical component for the cluster so it would be safe to have some guaranteed resources as well as allowing the users to define them based on their needs. In this commit, we init default requested resources and add the capability of user-defined values. Signed-off-by: dntosas <ntosas@gmail.com>
2de7866
to
5552493
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Cilium as a CNI is a critical component for the cluster so it would be safe
to have some guaranteed resources as well as allowing the users to
define them based on their needs.
In this commit, we init default requested resources and add the
capability of user-defined values.